Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1267

reference
669-tree-1
name
1267
tree-preservation-order

undefined

669-tpo-1
uprn
address-text
point
POINT (-1.016703 50.882244)
geometry
MULTIPOLYGON (((-1.016632 50.882237,-1.016636 50.882250,-1.016645 50.882263,-1.016661 50.882273,-1.016681 50.882280,-1.016703 50.882282,-1.016725 50.882280,-1.016744 50.882274,-1.016760 50.882264,-1.016771 50.882252,-1.016775 50.882238,-1.016771 50.882224,-1.016761 50.882211,-1.016746 50.882201,-1.016726 50.882195,-1.016704 50.882192,-1.016682 50.882194,-1.016662 50.882200,-1.016647 50.882210,-1.016636 50.882223,-1.016632 50.882237)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL